<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head><meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1">
<title>Low Power Application</title>
<style type="text/css">
	body {
		color: black;
		background: white;
		margin: 20px;
	}
	
	body, td {
		font-size: 90%;
	}

	body, h1, h2, h3, h4, h5, h6, p, center, td, th, ul, dl, div {
		font-family: Geneva, Arial, Helvetica, sans-serif;
	}

	h1 {
		display: block;
		text-align: center;
		font-size: 160%;
		margin: 0.67em 0px;
		font-weight: bold;
	}

	p {
		display: block;
		margin: 1em 0px;
	}
</style>
</head>
<body>
<h1>Low Power Networking Application</h1>

<p>This sample application demonstrates several important ZigBee PRO functionalities:</p>
<ul>
	<li>Power management schemes: scheduled and interrupt-based device awakening;</li>
    <li>Data collection from low-power devices on the central coordinator node;</li>
	<li>Data delivery from parent device (coordinator in this example) to children end devices via polling mechanism.</li>
</ul>

<p>One coordinator and at least one end device (maximum seven) can be engaged. Node identification, which consists of determining
device type and network address, is done differently depending on the platform.</p>

<p>After joining the network an end device transmits sensor data to the coordinator and enters the sleeping mode. Then it periodically wakes up
with a configurable interval and sends sensor data to the coordinator. Data transmission on the end device as well as data reception
on the coordinator are indicated by special LEDs.</p>

<p>Upon data frame reception the coordinator node forwards its data to the USART1 interface.
Thus if the coordinator is connected to PC via USB cable this information can be observed in a terminal window (e.g. Windows HyperTerminal).</p>

<p>The coordinator is able to configure the type of the sensor that end devices use for data reports. By default the value measured on
a temperature sensor is sent by each end device. The coordinator can be consequently switched to use one of the following sensors:
temperature sensor, battery status, light sensor.</p>

<p> Note that if an end device is sleeping the coordinator receives a command to change observed sensor type,
the sensor switch command is buffered on 
the parent node (in this example it is the coordinator) and is delivered to the end device
when it wakes up and retrieves it via the polling mechanism.</p>

<p>For detailed information please refer to <i>BitCloud API Reference</i></p>
</body>
</html>

